Prepaid load with account linking

ABSTRACT

Embodiments of the present invention relate to linking a prepaid account with a payment account used to fund the prepaid account. In some embodiments, during payment for a prepaid device, an authorization request message may include a prepaid account identifier associated with the prepaid account. In some embodiments, an activation request message may include a payment account identifier associated with the payment account. A server at the payment processing network may store an association between the prepaid account identifier and the payment account identifier in an account link database. In some embodiments of the invention, if the payment account is canceled, the payment processing network may use the account link database to cancel any associated prepaid accounts, and may transfer funds associated with corresponding prepaid accounts to an issuer associated with the payment account.

CROSS-REFERENCES TO RELATED APPLICATIONS

This application is a continuation application of U.S. application Ser.No. 14/103,702, filed Dec. 11, 2013 which is a non-provisionalapplication of and claims priority to U.S. Provisional Application No.61/735,960 titled “Prepaid Load With Account Linking,” filed Dec. 11,2012, which is herein incorporated by reference in its entirety for allpurposes.

BACKGROUND

Prepaid cards are growing in popularity as a means of providing payment.A prepaid card may be an open-loop branded card such as a Visa™ orMasterCard™, or may be merchant-branded, such as a gift certificate fora specific store. Prepaid cards provide several advantages to consumerssuch as convenience, security, and easy management.

However, fraud involving prepaid cards is an issue for consumers,merchants, and card issuers. Unauthorized persons may use stolen ormisappropriated credit card information to buy prepaid cards. Thisallows unauthorized persons to quickly put large charges on creditcards. Even though a credit card may be canceled when the unauthorizedcharges are discovered, the prepaid cards bought with the stolen creditcard information can still be used to make purchases after the creditcard is canceled, prolonging the damage associated with the fraud.

In addition, prepaid cards may be used to perform money laundering. Forexample, a legitimate credit card may be monitored by law enforcementagencies. However, if a prepaid card is bought using the legitimatecredit card and used for illicit activity, such activity may beconcealed. Thus, prepaid cards may be used to obfuscate the use offunds.

Embodiments of the present invention address these problems and otherproblems individually and collectively.

SUMMARY

Embodiments of the present invention broadly described relate to linkinga prepaid account with a payment account used to fund or pay for theprepaid account. In some embodiments, during payment for a prepaiddevice, an authorization request message may include a prepaid accountidentifier associated with the prepaid account. In some embodiments, anactivation request message may include a payment account identifierassociated with the payment account. A server at the payment processingnetwork may store an association between the prepaid account identifierand the payment account identifier in an account link database. In someembodiments of the invention, if the payment account is canceled, thepayment processing network may use the account link database to cancelany associated prepaid devices, and may transfer funds associated withcorresponding prepaid accounts to an issuer associated with the paymentaccount.

One embodiment of the invention discloses a server computer. The servercomputer comprises a processor and a non-transitory computer-readablestorage medium, comprising code executable by the processor forimplementing a method comprising receiving a prepaid account identifierassociated with a prepaid account and a payment account identifierassociated with a payment account used to fund or to pay for the prepaidaccount, and linking the prepaid account to the payment account usingthe prepaid account identifier and the payment account identifier,wherein the prepaid account identifier is retrievable using the paymentaccount identifier.

One embodiment of the invention discloses a method comprising receivinga prepaid account identifier associated with a prepaid account and apayment account identifier associated with a payment account used tofund or to pay for the prepaid account, and linking the prepaid accountto the payment account using the prepaid account identifier and thepayment account identifier, wherein the prepaid account identifier isretrievable using the payment account identifier.

One embodiment of the invention discloses a method comprising receivinga prepaid account identifier associated with a prepaid account and apayment account identifier associated with a payment account used tofund or to pay for the prepaid account, and sending a message comprisingthe prepaid account identifier and the payment account identifier,wherein the prepaid account is linked to the payment account, andwherein the prepaid account identifier is retrievable using the paymentaccount identifier.

These and other embodiments of the invention are described in furtherdetail below.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows an exemplary system that may be used with embodiments ofthe invention, whereby a payment device is used to conduct atransaction.

FIG. 2 illustrates an exemplary account link database.

FIG. 3 shows a flow diagram for authorizing funds and activating aprepaid account in some embodiments of the invention.

FIG. 4 shows a method for linking a prepaid account and a paymentaccount in some embodiments of the invention.

FIG. 5 shows another method for linking a prepaid account and a paymentaccount in some embodiments of the invention.

FIG. 6 shows a method for cancelling a prepaid account.

FIG. 7 shows an exemplary payment device.

FIG. 8 shows a block diagram of an exemplary computer apparatus.

DETAILED DESCRIPTION

Embodiments of the present invention relate to linking a prepaid accountwith a payment account used to fund or pay for the prepaid account.

In some embodiments, during a payment transaction for a prepaid device,an authorization request message may include a prepaid accountidentifier associated with the prepaid device, such as a primary accountnumber (PAN) of the prepaid device. In some embodiments, an activationrequest message may include a payment account identifier associated witha payment account, such as the PAN of the payment device used to providefunds for the prepaid device. A server at the payment processing networkmay store an association between the prepaid account identifier and thepayment account identifier in an account link database. In someembodiments of the invention, if the payment account is canceled, thepayment processing network may use the account link database to cancelany associated prepaid devices, and may transfer funds associated withcorresponding prepaid accounts to an issuer associated with the paymentaccount.

Prior to further description of embodiments of the invention,description of some terms may be helpful in understanding embodiments ofthe invention.

A “payment account” may include any account suitable to conduct paymenttransactions. A payment account may be associated with a “paymentdevice” and/or a “payment account identifier.” For example, a paymentaccount may be a credit card account, a checking account, or a debitcard account.

A “payment account identifier” may include any identifier or other datasuitable to identify a payment account. For example, a payment accountidentifier may be a primary account number (PAN), a bank account number,or a username. In some cases, a payment account identifier may beembossed on or be included in or stored on a payment device.

A “payment device” may include any device or apparatus operable toconduct payment transactions using a payment account. Examples ofpayment devices may include credit cards, debit cards, contactlessdevices, and mobile devices, payment checks, etc.

A “prepaid account” (which may be associated with a “prepaid device” anda “prepaid account identifier”) may include any account funded with anamount of currency. Examples of prepaid accounts may include a gift cardaccount, a debit card account, and an account associated with astored-value card. A prepaid account may be closed-loop (i.e., operableonly at a set of merchants), open-loop (i.e., operable through a paymentprocessing network such as Visa™ or MasterCard™), or operable in anyother suitable manner.

A “prepaid account identifier” may include any identifier or other datasuitable to identify a prepaid account. In some cases, a prepaid accountidentifier may be embossed on or be included in or stored on a prepaiddevice.

A “prepaid device” may be any device associated with a prepaid account.Examples of prepaid devices may include stored-value cards, merchantcards, gift cards, gift certificates, and debit cards, etc.

In some embodiments, the prepaid account may be loaded with a certainamount of funds during a purchase transaction. For example, the prepaiddevice may be sold at a merchant such as a retail establishment.

As used herein, a “account link database” may be any suitable databaseused to link a payment account to one or more prepaid accounts funded orpaid for by the payment account. The account link database may beoperable to retrieve one or more prepaid account identifiers using apayment account identifier, and to retrieve one or more payment accountidentifiers using a prepaid account identifier.

Embodiments of the invention enable an issuer, user, or other party tocancel prepaid accounts linked to a payment account in the event offraud. Specifically, embodiments of the invention allow a prepaidaccount identifier linked to a payment account identifier to beretrieved. The prepaid account identifiers may then be used to cancelthe prepaid account and transfer remaining funds in the account to anissuer computer associated with the payment account. This reduces thedamage caused by fraudulent purchases of prepaid devices made withstolen or misappropriated payment account information and reduces theincentive for criminals to perform payment account fraud.

Embodiments of the invention can also counteract the use of prepaiddevices to launder money. The account link database may allow lawenforcement or other parties to determine prepaid accounts linked to apayment account. The transactions of these prepaid devices may beinspected to determine activities that may otherwise have beenobfuscated from law enforcement or other parties monitoring the paymentaccount.

Embodiments of the invention also provide the technical advantage ofautomatically generating an account link database comprising prepaidaccounts linked to payment accounts. For example, a merchant computermay provide both a payment account identifier and a prepaid accountidentifier in an authorization request message requesting funds for aprepaid account, or in an activation request message requestingactivation of the prepaid account. In some embodiments, the accountidentifiers can be received by a payment processing network and used tolink a prepaid account to a payment account in an account link database.Thus, the account link database may be populated with minimal if anymanual effort through an extension of existing messages used in paymenttransactions. The account link database may also be used to enable otherfunctionality, such as facilitating loading funds from a payment accountto a linked prepaid account.

Embodiments of the invention provide the further technical advantage oflinking a prepaid account and a payment account without requiring theaccounts to be associated with the same issuer, payment processingnetwork, or payment type. Users may use a large variety of paymentaccounts to purchase a prepaid device, such as credit card accounts,checking accounts, online money transfer accounts, mobile paymentaccounts, wire transfer accounts, etc. Each of these payment accountsmay have a differing payment method, and the payment methods may notshare any common party. Prepaid accounts are similarly diverse; they mayinclude stored-value accounts, gift card accounts, transit accounts,etc. However, as long as either authorization for funding the prepaidaccount or activation of prepaid account is conducted via a paymentaccount associated with the prepaid account or the payment account,embodiments of the invention enable the accounts to be linkedautomatically.

I. Exemplary Payment Systems and Methods

FIG. 1 shows an exemplary system for using embodiments of the invention.The system includes a payment device 110 comprising a payment accountidentifier 111, a prepaid device 120 comprising a prepaid accountidentifier 121, an access device 130, a merchant computer 140, anacquirer computer 150 associated with the merchant 140, a paymentprocessing network 160 connected to an account link database 200, and apayment account issuer computer 170. In a payment transaction, a user(not shown) may purchase services or goods such as a prepaid device 120at the merchant computer 140 using payment device 110. The user may bean individual, or an organization such as a business that is capable ofpurchasing goods or services. The acquirer computer 150 can communicatewith an payment account issuer computer 170 via a payment processingnetwork 160.

A user (not shown) may use the payment device 110, for example, to makepurchases. In one example, payment device 110 may be in the form of apayment card. The payment device may be associated with an issuerassociated with payment account issuer computer 170.

The issuer is typically a business entity (e.g., a bank) which maintainsfinancial accounts for the user and often issues a payment device suchas a credit or debit card to the user. A merchant is typically anentity, such as a store, person, or service provider, that engages intransactions. An acquirer is typically a business entity, e.g., acommercial bank that has a business relationship with a particularmerchant or other entity. Some entities can perform both issuer andacquirer functions. Embodiments of the invention encompass such singleentity issuer-acquirers.

The payment processing network 160 may include data processingsubsystems, networks, and operations used to support and deliverauthorization services, exception file services, and clearing andsettlement services. An exemplary payment processing network may includeVisaNet™. Payment processing networks such as VisaNet™ are able toprocess credit card transactions, debit card transactions, and othertypes of commercial transactions. VisaNet™, in particular, includes aVIP system (Visa Integrated Payments system) which processesauthorization requests and a Base II system which performs clearing andsettlement services.

The payment processing network 160 may include a server computer. Aserver computer is typically a powerful computer or cluster ofcomputers. For example, the server computer can be a large mainframe, aminicomputer cluster, or a group of servers functioning as a unit. Inone example, the server computer may be a database server coupled to aWeb server. The payment processing network 160 may use any suitablewired or wireless network, including the Internet.

The merchant computer 140 may also include, or may receivecommunications from, an access device 130 that can interact with thepayment device 110 and/or prepaid device 120. The access device 130according to embodiments of the invention can be in any suitable form.Examples of access devices include point of sale (POS) devices, cellularphones, PDAs, personal computers (PCs), tablet PCs, handheld specializedreaders, set-top boxes, electronic cash registers (ECRs), automatedteller machines (ATMs), virtual cash registers (VCRs), kiosks, securitysystems, access systems, and the like.

If the access device 130 is a point of sale terminal, any suitable pointof sale terminal including card readers may be used. The card readersmay include any suitable contact or contactless mode of operation. Forexample, exemplary card readers can include RF (radio frequency)antennas, magnetic stripe readers, etc. to interact with the paymentdevice 110 or prepaid device 120.

The payment device 110 and prepaid device 120 may interact with accessdevice 130 to electronically communicate a payment account identifier111 or a prepaid account identifier 121 to the access device 130,respectively. The interaction may be initiated, in various embodiments,by swiping, tapping, bringing in proximity, or otherwise operatingdevices 110 and 120.

In some payment transactions, the user purchases a good or service atmerchant 140 using a payment device 110. The user's payment device 110can interact with an access device 130 at a merchant associated withmerchant computer 140. For example, the user may swipe the paymentdevice 200 at a card reader in the access device 130. Alternatively, theuser may indicate payment details to the merchant electronically, suchas in an online transaction.

An authorization request message may be generated by payment device 110or merchant computer 140 and then forwarded to the acquirer computer150. After receiving the authorization request message, theauthorization request message is then sent to the payment processingnetwork 160. The payment processing network 160 then forwards theauthorization request message to the corresponding payment accountissuer computer 170.

An “authorization request message” may be an electronic message that issent to request authorization for a transaction. The authorizationrequest message may be sent to a payment processing network and/or anissuer of a payment card. An authorization request message according tosome embodiments may comply with ISO 8583, which is a standard forsystems that exchange electronic transaction information associated witha payment made by a user using a payment device or payment account. Theauthorization request message may include an issuer account identifier(e.g., a payment account identifier) that may be associated with apayment device or payment account. An authorization request message mayalso comprise additional data elements corresponding to “identificationinformation” including, by way of example, a service code, a CVV (cardverification value), a dCVV (dynamic card verification value), anexpiration date, etc. An authorization request message may also comprise“transaction information,” such as any information associated with acurrent transaction, such as the transaction amount, merchantidentifier, merchant location, etc., as well as any other informationthat may be utilized in determining whether to identify and/or authorizea transaction. The authorization request message may also include otherinformation such as information that identifies the access device thatgenerated the authorization request message, information about thelocation of the access device, etc.

After the payment account issuer computer 170 receives the authorizationrequest message, the payment account issuer computer 170 sends anauthorization response message back to the payment processing network160 to indicate whether the current transaction is authorized (or notauthorized). The payment processing network 160 then forwards theauthorization response message back to the acquirer computer 150. Insome embodiments, payment processing network 160 may decline thetransaction even if payment account issuer computer 170 has authorizedthe transaction, for example depending on a value of the fraud riskscore. The acquirer computer 150 then sends the response message back tothe merchant computer 140.

An “authorization response message” may be an electronic message replyto an authorization request message. The authorization response messagemay be generated by an issuing financial institution 170 or a paymentprocessing network 160. The authorization response message may include,by way of example, one or more of the following status indicators:Approval—transaction was approved; Decline—transaction was not approved;or Call Center—response pending more information, merchant must call thetoll-free authorization phone number. The authorization response messagemay also include an authorization code, which may be a code that acredit card issuing bank returns in response to an authorization requestmessage in an electronic message (either directly or through the paymentprocessing network 160) to the merchant computer 140 that indicatesapproval of the transaction. The code may serve as proof ofauthorization. As noted above, in some embodiments, a payment processingnetwork 160 may generate or forward the authorization response messageto the merchant.

After the merchant computer 140 receives the authorization responsemessage, the merchant computer 140 may then provide the authorizationresponse message for the user. The response message may be displayed bythe access device 130, or may be printed out on a physical receipt.Alternately, if the transaction is an online transaction, the merchantmay provide a web page or other indication of the authorization responsemessage as a virtual receipt. The receipts may include transaction datafor the transaction.

At the end of the day, a normal clearing and settlement process can beconducted by the payment processing network 160. A clearing process is aprocess of exchanging financial details between an acquirer and anissuer to facilitate posting to a customer's payment account andreconciliation of the user's settlement position.

FIG. 2 shows an exemplary account link database 200. Account linkdatabase 200 may be used to store data linking prepaid accounts andpayment accounts.

Account link database 200 may comprise a plurality of fields, includinga prepaid account identifier 201, payment account identifier 202,prepaid account issuer identifier 203, payment account issuer identifier204, date of activation 205, and activation amount 206. Account linkdatabase 200 may comprise a plurality of records, each including valuesfor at least one of fields 201-206.

Prepaid account identifier 201 may include any suitable prepaid accountidentifier (e.g., prepaid account identifier 121) or other data suitableto identify a prepaid account. In some embodiments, account linkdatabase 200 may be indexed by prepaid account identifier 201, so thatrecords matching a prepaid account identifier may be quickly determined.

Payment account identifier 202 may include any payment accountidentifier (e.g., payment account identifier 111) linked to a prepaidaccount identifier 201. In some embodiments, account link database 200may be indexed by payment account identifier 202, so that recordsmatching a payment account identifier may be quickly determined.

Prepaid account issuer identifier 203 may include any identifiersuitable to identify an issuer associated with a prepaid accountidentifier 201. For example, the prepaid account issuer identifier maybe a bank identification number (BIN), a routing number, or any othersuitable identifier. In some embodiments, prepaid account issueridentifier 203 may be used to determine a prepaid account issuercomputer 180 to communicate with regarding the prepaid account, forexample during step 603 of the method of FIG. 6.

Payment account issuer identifier 204 may include any identifiersuitable to identify an issuer associated with a payment accountidentifier 202. For example, the payment account issuer identifier maybe a bank identification number (BIN), a routing number, or any othersuitable identifier. In some embodiments, payment account issueridentifier 204 may be used to determine a payment account issuercomputer 170 to communicate with regarding the payment account, forexample during step 605 of the method of FIG. 6.

Date of activation 205 may include any date, time, timestamp, or otherdata indicating when a prepaid account associated with prepaid accountidentifier 201 was activated. Date of activation 205 may, in someembodiments, be a time at which an authorization response messageapproving funds for the prepaid account was generated or received, or atime at which an activation response message activating the prepaidaccount was generated or received. In some embodiments, date ofactivation 205 may be used to conditionally cancel prepaid accounts. Forexample, if a credit card used for funding prepaid accounts wasindicated as lost or stolen on Jan. 6, 2013, then only prepaid accountsactivated on or after Jan. 6, 2013 may be canceled. Prepaid accountsactivated before Jan. 6, 2013 may remain valid because such prepaidaccounts may have been valid purchases made by the authorized creditcardholder.

Activation amount 206 may include any number or other indication of anamount of currency used to fund the prepaid account. In someembodiments, activation amount 206 may include a currency and monetaryused for funding (e.g., $250 USD). Activation amount 206 may in someembodiments be determined from an authorization request message or anactivation request message.

II. Exemplary Prepaid Account Funding Methods

FIG. 3 shows a flow diagram 300 for authorizing funds and activating aprepaid account in some embodiments of the invention.

At step 301, access device 130 sends a payment account identifier 111associated with a with a payment account, and prepaid account identifier121 associated with a prepaid account to a merchant computer 140. Insome embodiments, the identifiers 111 and 121 may be read from devices110 and 120, respectively, by the access device 130. For example, insome embodiments, the merchant may swipe or tap the devices 110 and 120on access device 130. In other embodiments, the merchant may manuallyenter a payment account identifier 111 or prepaid account identifier 121into the access device 130 (e.g., using a keypad). The merchant may alsoenter a desired amount of funds to be loaded to the prepaid account intoaccess device 130.

At step 302, merchant computer 140 generates and sends an authorizationrequest message requesting funds from the payment account for activationof the prepaid account. The authorization request message may includethe payment account identifier 111. In some embodiments, theauthorization request message may be sent to an acquirer computer 150,which may forward the message to payment processing network 160.

At step 303, payment processing network 160 receives and processes theauthorization request message. In addition, at step 303 paymentprocessing network 160 determines a payment account issuer computer 170associated with payment account identifier 111 received in theauthorization request message.

At step 304, payment processing network 160 forwards the authorizationrequest message to the determined payment account issuer computer 170.Payment account issuer computer 170 may then process the authorizationrequest and determine whether to approve or decline the request. Thedetermination may be made based on a variety of factors, such as theaccount balance of the payment account and the likelihood that theauthorization request is fraudulent.

At step 305, payment account issuer computer 170 sends to paymentprocessing network 160 an authorization response message including anindication of whether authorization is approved or declined.

At step 306, the authorization response message is sent to acquirercomputer 150. At step 307, the authorization response is sent tomerchant computer 140.

At step 308, payment processing network 160 stores the payment accountidentifier 111 in account link database 200.

At step 309, if the authorization response message indicates thatfunding is approved, merchant computer 140 generates and sends anactivation request message requesting activation of the prepaid account.Typically, the activation request message includes the prepaid accountidentifier 121. In some embodiments, the activation request message maybe sent to an acquirer computer 150, which may forward the message topayment processing network 160.

At step 310, payment processing network 160 receives and processes theactivation request message. In addition, at step 310 payment processingnetwork 160 determines a prepaid account issuer computer 180 associatedwith prepaid account identifier 121 included in the activation requestmessage.

At step 311, payment processing network 160 forwards the activationrequest message to the determined prepaid account issuer computer 180.Prepaid account issuer computer 180 may then process the activationrequest and determine whether to activate the prepaid account. Thedetermination may be made based on a variety of factors, such as theauthorization of funds and the likelihood that the activation request isfraudulent.

At step 312, prepaid account issuer computer 180 sends to paymentprocessing network 160 an activation response message including anindication of whether the prepaid account has been activated.

At step 313, the activation response message is sent to acquirercomputer 150. At step 314, the activation response is sent to merchantcomputer 140, which may then notify the user that the prepaid accounthas been activated.

At step 315, payment processing network 160 stores the prepaid accountidentifier 121 in account link database 200.

The method of FIG. 3 may link the prepaid account to the payment accountin any suitable manner. For example, in some embodiments, a transactionidentifier associated with the authorization for funds from the paymentaccount may be saved in account link database 200 in a record associatedwith the payment account identifier and returned to merchant computer140. Merchant computer 140 may include the transaction identifier in theactivation request message. Subsequently, payment processing network 160may use the transaction identifier to retrieve the corresponding recordin the account link database 200 and link the accounts.

In some embodiments, subsequent to step 315, merchant computer 140 maytransmit an additional message to payment processing network 160indicating the prepaid account identifier 121 and payment accountidentifier 111 to be linked. Additional methods 400 and 500 for linkingthe prepaid account to the payment account are shown in FIGS. 4 and 5,respectively.

FIG. 4 shows a method 400 for linking a prepaid account and a paymentaccount in some embodiments of the invention. Steps 401-408 of method400 are similar to the corresponding method steps 301-308 illustrated inFIG. 3. However, the addition of a prepaid account identifier 121 in theauthorization request message allows payment processing network 160 tolink the prepaid account to the payment account.

At step 401, merchant computer 140 receives a payment account identifier111 associated with a with a payment account, and prepaid accountidentifier 121 associated with a prepaid account. The payment accountidentifier 111 and prepaid account identifier 121 may be received in anysuitable manner, including those described above for step 302 in themethod of FIG. 3.

At step 402, merchant computer 140 generates and sends an authorizationrequest message requesting funds for activation from the paymentaccount. In addition to the payment account identifier 111, theauthorization request message comprises prepaid account identifier 121.In some embodiments, prepaid account identifier 121 may be included inan existing field in the authorization request message. For example, inauthorization request messages adhering to the InternationalOrganization for Standardization (ISO) 8583 standard, field 104(“Transaction Description”) may include the prepaid account identifier121. In other cases, the prepaid account identifier 121 may be includedin fields 102 or 103 (“Account Identification” 1 and 2, respectively).In other cases, the prepaid account identifier 121 may be included infield 124 (“Info text”). In other embodiments, other existing fields ora new field may be defined for the prepaid account identifier 121.

The authorization request message may be sent to an acquirer computer150, which may forward the message to payment processing network 160.

At step 403, payment processing network 160 receives the authorizationrequest message comprising the payment account identifier 111 and theprepaid account identifier 121. In some embodiments, payment processingnetwork 160 may store a provisional record in the account link database200 including the identifiers 111 and 121. For example, the prepaidaccount identifier 121 may be stored in field 201, and the paymentaccount identifier 111 may be stored in field 202. In addition, aprepaid account issuer identifier and a payment account issueridentifier may be determined from the authorization request message andstored in corresponding fields 203 and 204, respectively. The date ofactivation 205 and activation amount 206 for the record may be leftblank, since the prepaid account has not been activated.

In addition, at step 403 payment processing network 160 determines apayment account issuer computer 170 associated with payment accountidentifier 111 included in the authorization request.

At step 404, payment processing network 160 forwards the authorizationrequest message to the determined payment account issuer computer 170.In some embodiments, the payment processing network 160 may remove theprepaid account identifier 121 from the forwarded authorization requestmessage. The prepaid account identifier 121 may be removed for a varietyof reasons, such as allowing the authorization request message to besent to the payment account issuer computer 170 in a standard format, orfor privacy of the prepaid account identifier 121.

Once the payment account issuer computer 170 receives the authorizationrequest message, the issuer computer 170 may process the authorizationrequest and determine whether to approve or decline the request.

At step 405, payment account issuer computer 170 sends an authorizationresponse message to payment processing network 160 including anindication of whether authorization is approved or declined.

At step 406, the payment processing network 160 processes and sends theauthorization response message. The authorization response may be sentvia an acquirer computer 150. At step 407, merchant computer 140receives the authorization response message.

At step 408, if the authorization response message indicates thatfunding is approved, payment processing network 160 links the prepaidaccount to the payment account using the prepaid account identifier 121and the payment account identifier 111. Linking the prepaid account tothe payment account may cause, for example, payment processing network160 to finalize the provisional record stored in account link database200 by updating the date of activation 205 and activation amount 206.Thus, after step 408, the prepaid account and payment account arelinked.

At step 409, if the authorization response message indicates thatfunding is approved, merchant computer 140 activates the prepaidaccount. In some embodiments, activating the prepaid account may includesteps 309-314 as described for FIG. 3. In other embodiments, activatingthe prepaid account may include steps 509-515 as described for FIG. 5.In yet other embodiments, activation may be performed using anothermethod (e.g., a closed-loop activation procedure).

FIG. 5 shows a method 500 for linking a prepaid account and a paymentaccount in some embodiments of the invention. Steps 509-514 of method500 are similar to the corresponding method steps 309-314 illustrated inFIG. 3. However, the addition of a payment account identifier 111 in theactivation request message allows payment processing network 160 to linkthe prepaid account to the payment account.

At step 501, merchant computer 140 receives a payment account identifier111 associated with a with a payment account, and prepaid accountidentifier 121 associated with a prepaid account. The payment accountidentifier 111 and prepaid account identifier 121 may be received in anysuitable manner, including those described above for step 302 in themethod of FIG. 3.

At step 502, merchant computer 140 authorizes funding for the prepaidaccount. In some embodiments, authorizing funding for the prepaidaccount may include steps 302-308 as described for FIG. 3. In otherembodiments, authorizing funding for the prepaid account may includesteps 402-408 as described for FIG. 4. In yet other embodiments, fundingfor the prepaid account may be performed using another method (e.g., anonline payment, personal check, or wire transfer).

At step 509, if funding for the prepaid account is authorized, merchantcomputer 140 generates and sends an activation request messagerequesting activation of the prepaid account. In addition to the prepaidaccount identifier 121, the activation request message includes thepayment account identifier 111.

In some embodiments, payment account identifier 111 may be included inan existing field in the activation request message. For example, inactivation request messages adhering to the International Organizationfor Standardization (ISO) 8583 standard, field 104 (“TransactionDescription”) may include the payment account identifier 111. In othercases, the payment account identifier 111 may be included in fields 102or 103 (“Account Identification” 1 and 2, respectively). In other cases,the payment account identifier 111 may be included in field 124 (“Infotext”). In other embodiments, a new field may be defined for the paymentaccount identifier 111.

In some embodiments, the activation request message may be sent to anacquirer computer 150, which may forward the message to paymentprocessing network 160.

At step 510, payment processing network 160 receives and processes theactivation request message. In some embodiments, payment processingnetwork 160 may store a provisional record in the account link database200 including payment account identifier 111 and prepaid accountidentifier 121. For example, the prepaid account identifier 121 may bestored in field 201, and the payment account identifier 111 may bestored in field 202. In addition, a prepaid account issuer identifierand a payment account issuer identifier may be determined from theactivation request message and stored in corresponding fields 203 and204, respectively. The date of activation 205 and activation amount 206for the record may be left blank, since the prepaid account has not yetbeen activated.

In some cases, such as if step 502 was performed in accordance withsteps 402-408 of FIG. 4 during authorization of funds for activation ofthe prepaid account, a record in account link database 200 may alreadyexist for the payment account identifier 111 and prepaid accountidentifier 121. In such cases, a new provisional record may not becreated in order to avoid duplication of data.

In addition, at step 510 payment processing network 160 determines aprepaid account issuer computer 180 associated with prepaid accountidentifier 121 included in the activation request message.

At step 511, payment processing network 160 forwards the activationrequest message to the determined prepaid account issuer computer 180.In some embodiments, the payment processing network 160 may remove thepayment account identifier 111 from the forwarded activation requestmessage. The payment account identifier 111 may be removed for a varietyof reasons, such as allowing the activation request message to be sentto the prepaid account issuer computer 180 in a standard format, or forprivacy of the payment account identifier 111. Prepaid account issuercomputer 180 may then process the activation request and determinewhether to activate the prepaid account.

At step 512, prepaid account issuer computer 180 sends to paymentprocessing network 160 an activation response message including anindication of whether the prepaid account has been activated.

At step 513, the activation response message is sent to acquirercomputer 150. At step 514, the activation response is sent to merchantcomputer 140, which may then notify the user whether the prepaid accounthas been activated.

At step 515, if the activation response message indicates that theprepaid account has been activated, payment processing network 160 linksthe prepaid account and payment account in the account link database.Linking the prepaid account to the payment account may cause, forexample, payment processing network 160 to finalize the provisionalrecord stored in account link database 200 by updating the date ofactivation 205 and activation amount 206. Thus, after step 515, theprepaid account and payment account are linked.

In some cases, such as if a record already exists in account linkdatabase 200 indicating that the prepaid account and payment account arelinked, at step 515 the record may be updated with new data (e.g., thetime at which the activation response message was generated or received,or the final activation amount for the prepaid account).

It should be noted that FIGS. 3-5 are intended to be descriptive, butnot limiting. For example, although the prepaid account and paymentaccount are described above as being linked in step 408 of method 400,and step 515 of method 500, in various embodiments the accounts may belinked at other suitable times. For example, the payment account andprepaid account may be linked once the corresponding authorizationresponse message (for method 400) or activation response message (formethod 500) is received by payment processing network 160 (e.g., at step406 or 513). Alternatively, the accounts may be linked once theauthorization request message (for method 400) or activation requestmessage (for method 500) is received by payment processing network 160(e.g., at step 403 or 510). Such embodiments may have the advantage ofrequiring less processing.

III. Exemplary Account Cancelling Methods

FIG. 6 shows a method 600 for cancelling a prepaid account. Method 600may be performed for a prepaid account that has been previously linkedto a payment account (e.g., through methods 400 or 500). The paymentaccount may be canceled for any suitable reason, such as upon thedetection of fraudulent charges on the payment account.

At step 601, payment account issuer computer 170 sends a cancellationrequest message to payment processing network 160 including the paymentaccount identifier 111 for the payment account to be canceled. In someembodiments, the cancellation request message may include a date ofcompromise indicating the date of when a payment account may have beencompromised. Prepaid accounts activated after the date of compromise canbe canceled.

At step 602, payment processing network 160 retrieves a prepaid accountidentifier 121 linked to the received payment account identifier 111using the account link database 200. In some embodiments, an index maybe used to determine records with a payment account identifier field 202matching the received payment account identifier 111. In some cases,multiple records may match, indicating multiple prepaid accounts linkedto the payment account. For each matching record, the prepaid accountidentifier 201 is determined.

At step 603, payment processing network 160 initiates cancellation ofthe prepaid account associated with the retrieved prepaid accountidentifier 201. In some embodiments, initiating the cancellation mayinvolve sending cancellation request messages to prepaid account issuercomputers 180 associated with the prepaid accounts. In some embodiments,payment processing network 160 may compare the date of compromise to thedate of activation 206 in the matched records, and initiate cancellationof only those of the prepaid accounts that were activated on or afterthe date of compromise. This may allow legitimate prepaid accountsfunded before the date of compromise to remain valid and usable.

At step 604, prepaid account issuer computer 180 cancels the prepaidaccount. Cancellation of the prepaid account may include, for example,freezing the funds in the prepaid account and preventing any furthertransactions using the prepaid account.

In some embodiments, at step 605, prepaid account issuer computer 180may transfer any remaining funds in the canceled prepaid account to thepayment account issuer. In some embodiments, the funds may betransferred to the payment account, sent to the user associated with thepayment account (e.g., as a check), or may be kept (e.g., in escrow) bythe payment account issuer if the payment account is compromised.

IV. Additional Embodiments

In some embodiments of the invention, account link database 200 may beused for purposes other than those described above. For example, theaccount link database 200 may be used to facilitate reloading prepaidaccounts using funds associated with the payment account. In someembodiments, if an account balance for a prepaid account drops below athreshold value, the prepaid account may be re-loaded with funds fromthe linked payment account stored in account link database 200.

V. Exemplary Computer Apparatus

FIG. 7 shows an example of a payment device 101″ in the form of a card.As shown, the payment device 101″ comprises a plastic substrate 101(m).In some embodiments, a contactless element 101(o) for interfacing withan access device 102 may be present on, or embedded within, the plasticsubstrate 101(m). User information 101(p) such as an account number,expiration date, and/or a user name may be printed or embossed on thecard. A magnetic stripe 101(n) may also be on the plastic substrate101(m). In some embodiments, the payment device 101″ may comprise amicroprocessor and/or memory chips with user data stored in them.

As noted above and shown in FIG. 7, the payment device 101″ may includeboth a magnetic stripe 101(n) and a contactless element 101(o). In someembodiments, both the magnetic stripe 101(n) and the contactless element101(o) may be in the payment device 101″. In some embodiments, eitherthe magnetic stripe 101(n) or the contactless element 101(o) may bepresent in the payment device 101.

FIG. 8 is a high level block diagram of a computer system that may beused to implement any of the entities or components described above. Thesubsystems shown in FIG. 8 are interconnected via a system bus 875.Additional subsystems include a printer 803, keyboard 806, fixed disk807, and monitor 809, which is coupled to display adapter 804.Peripherals and input/output (I/O) devices, which couple to I/Ocontroller 800, can be connected to the computer system by any number ofmeans known in the art, such as a serial port. For example, serial port805 or external interface 808 can be used to connect the computerapparatus to a wide area network such as the Internet, a mouse inputdevice, or a scanner. The interconnection via system bus 875 allows thecentral processor 802 to communicate with each subsystem and to controlthe execution of instructions from system memory 801 or the fixed disk807, as well as the exchange of information between subsystems. Thesystem memory 801 and/or the fixed disk may embody a computer-readablemedium.

As described, the inventive service may involve implementing one or morefunctions, processes, operations or method steps. In some embodiments,the functions, processes, operations or method steps may be implementedas a result of the execution of a set of instructions or software codeby a suitably-programmed computing device, microprocessor, dataprocessor, or the like. The set of instructions or software code may bestored in a memory or other form of data storage element which isaccessed by the computing device, microprocessor, etc. In otherembodiments, the functions, processes, operations or method steps may beimplemented by firmware or a dedicated processor, integrated circuit,etc.

It should be understood that the present invention as described abovecan be implemented in the form of control logic using computer softwarein a modular or integrated manner. Based on the disclosure and teachingsprovided herein, a person of ordinary skill in the art will know andappreciate other ways and/or methods to implement the present inventionusing hardware and a combination of hardware and software.

Any of the software components or functions described in thisapplication may be implemented as software code to be executed by aprocessor using any suitable computer language such as, for example,Java, C++ or Perl using, for example, conventional or object-orientedtechniques. The software code may be stored as a series of instructions,or commands on a computer-readable medium, such as a random accessmemory (RAM), a read-only memory (ROM), a magnetic medium such as ahard-drive or a floppy disk, or an optical medium such as a CD-ROM. Anysuch computer-readable medium may reside on or within a singlecomputational apparatus, and may be present on or within differentcomputational apparatuses within a system or network.

While certain exemplary embodiments have been described in detail andshown in the accompanying drawings, it is to be understood that suchembodiments are merely illustrative of and not intended to berestrictive of the broad invention, and that this invention is not to belimited to the specific arrangements and constructions shown anddescribed, since various other modifications may occur to those withordinary skill in the art.

As used herein, the use of “a”, “an” or “the” is intended to mean “atleast one”, unless specifically indicated to the contrary.

What is claimed is:
 1. A server computer comprising: a processor; and anon-transitory computer-readable medium, comprising code executable bythe processor for implementing a method comprising: linking a prepaidaccount to a payment account by storing a record in an account linkdatabase connected to the server computer, the record comprising aprepaid account identifier and a payment account identifier, wherein theprepaid account identifier is retrievable using the payment accountidentifier; receiving a payment account cancellation request messageincluding the payment account identifier; retrieving the prepaid accountidentifier linked to the payment account identifier included in thepayment account cancellation request message; initiating cancellation ofthe prepaid account associated with the retrieved prepaid accountidentifier, wherein the payment account cancellation request messagefurther comprises a date of compromise of the payment account and theprepaid account is activated after the date of compromise; and inresponse to initiating cancellation of the prepaid account associatedwith the retrieved prepaid account identifier, initiating refunding offunds in the prepaid account to a payment account issuer associated withthe payment account to be cancelled.
 2. The server computer of claim 1,wherein the prepaid account identifier and the payment accountidentifier are received by the processor in an authorization requestmessage to fund the prepaid account, and wherein the method furthercomprises: sending, by the processor, the authorization request messageto a payment account issuer computer associated with the paymentaccount; and receiving, by the processor, an authorization responsemessage indicating that the funding is approved, wherein linking theprepaid account to the payment account is performed after the funding isapproved.
 3. The server computer of claim 2, wherein the prepaid accountidentifier is removed by the processor from the authorization requestmessage sent to the payment account issuer computer.
 4. The servercomputer of claim 1, wherein the prepaid account identifier and thepayment account identifier are received by the processor in anactivation request message to activate the prepaid account prior toreceiving the payment account cancellation request message, and whereinthe method further comprises: sending, by the processor, the activationrequest message to a prepaid account issuer computer associated with theprepaid account; and receiving, by the processor, an activation responsemessage indicating that the prepaid account is activated, whereinlinking the prepaid account to the payment account is performed afterthe prepaid account is activated.
 5. The server computer of claim 4,wherein the prepaid account identifier is removed by the processor fromthe activation request message sent to the prepaid account issuercomputer.
 6. A computer-implemented method comprising: receiving, by aprocessor, a payment account cancellation request message including apayment account identifier for a prepaid account; retrieving, by theprocessor, a prepaid account identifier linked to the payment accountidentifier included in the payment account cancellation request message;initiating, by the processor, cancellation of the prepaid accountassociated with the retrieved prepaid account identifier, wherein thepayment account cancellation request message further comprises a date ofcompromise of a payment account associated with the prepaid account andthe prepaid account is activated after the date of compromise; and inresponse to initiating cancellation of the prepaid account associatedwith the retrieved prepaid account identifier, initiating, by theprocessor, refunding of funds in the prepaid account to a paymentaccount issuer associated with the payment account to be cancelled. 7.The computer-implemented method of claim 6, wherein the prepaid accountidentifier and payment account identifier are received by the processorin an authorization request message to fund the prepaid account, andwherein the method further comprises: sending, by the processor, theauthorization request message to a payment account issuer computerassociated with the payment account; and receiving, by the processor, anauthorization response message indicating that the funding is approved,wherein linking of the prepaid account to the payment account isperformed after the funding is approved.
 8. The computer-implementedmethod of claim 7, wherein the prepaid account identifier is removed bythe processor from the authorization request message sent to the paymentaccount issuer computer.
 9. The computer-implemented method of claim 6,wherein the prepaid account identifier and payment account identifierare received by the processor in an activation request message toactivate the prepaid account prior to receiving the payment accountcancellation request message, and wherein the method further comprises:sending, by the processor, the activation request message to a prepaidaccount issuer computer associated with the prepaid account; andreceiving, by the processor, an activation response message indicatingthat the prepaid account is activated, wherein linking the prepaidaccount to the payment account is performed after the prepaid account isactivated.
 10. The computer-implemented method of claim 9, wherein theprepaid account identifier is removed by the processor from theactivation request message sent to the prepaid account issuer computer.